| Source Files (.tab) |
Drag and drop your file into the window, or click within the upload box and navigate to the file on your network.
A .zip archive can be uploaded if more than one file is required.
|
| Coordinate Reference System |
Coordinate Reference System parameters are required in a session that will write data to Oracle.
This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data, if it cannot be deduced automatically.
This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined).
See Coordinate Reference System for more information on when this is required.
|
| Allow invalid geometries |
Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported.
This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.
|
| Enable full 3D Geometries (BETA) |
Select to enable full 3D geometries.
Note: This parameter will only appear with an additional license enabling 3D support within 1Integrate. For more information on full 3D in 1Integrate, please see 3D Support.
|
| For X, Y, Z, M data: |
If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only.
Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.
|
| The following parameters are only necessary for FME connections (not GDAL): |
| Import FME Log File |
Download the FME log file created during import (to help identify any errors). |
| Fix ring direction and inclusion errors |
Polygon rings are assumed to be encoded using the right-hand rule, i.e. outer rings are anti-clockwise and inner rings are clockwise.
If the service does not guarantee that encoding, then set this flag to have polygon rings automatically oriented on import to avoid later problems when processing the data.
Note: This requires a small amount of additional processing so only set if the ring direction is not guaranteed.
|
| Reverse coordinate axis order (y, x) |
Reverse the x and y co-ordinate values. |
| Encoding |
Controls which character encoding is used to interpret text attributes.
If blank, the character encoding will be automatically detected.
|
| Clip to envelope |
If selected, causes features that overlap the bounding box to be clipped and the outer part discarded.
Note: This should only be used when a session is loading a subset of the data by defining an extent as a bounding box or polygon. If set, it causes features that overlap the extent to be clipped and the outer part discarded. If not selected then the whole geometry of features that intersect the extent will be loaded including the parts of their geometry that are outside the extent.
|
| FME table password |
This parameter is only applicable when opening datasets of Type FME. If the auxillary FME dataset is a database reader, then MapInfo willl not automatically put the password for the source database in the tab file. This parameter allows the user to specify the password dynamically.
If the password is hardcoded into the tab file, then this parameter will supercede that password.
|
| Exposed attributes |
Allows the selection of format attributes to be explicitly added to the reader feature type.
Enter a comma-separated list of attribute names and types that will be added to the schema features.
|
| For X, Y, Z, M data: |
If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only.
Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.
|
| Write ignored Z or M values as zero |
Select to write ignored values as zero in place of null. |
